chore(deps): bump @tiptap/core from 3.29.0 to 3.30.5 - #6134
chore(deps): bump @tiptap/core from 3.29.0 to 3.30.5#6134dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@tiptap/core](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/core) from 3.29.0 to 3.30.5. - [Release notes](https://github.com/ueberdosis/tiptap/releases) - [Changelog](https://github.com/ueberdosis/tiptap/blob/v3.30.5/packages/core/CHANGELOG.md) - [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.5/packages/core) --- updated-dependencies: - dependency-name: "@tiptap/core" dependency-version: 3.30.5 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
🟡 Waiting for changesLast updated: 2026-09-09 03:48 UTC |
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #6134 — @tiptap/core 3.29.0 → 3.30.5 (production dependency, minor + patches within 3.x). Low semver risk, no breaking changes in range. CI passing (frontend tests, asset build, browser smoke test, linting).
Security fixes — the reason to merge:
- GHSA-j95f-988m-3j2f (HIGH) — quadratic ReDoS in block/inline Markdown attribute parsing; affects
>= 3.7.0, < 3.30.5. - GHSA-cp6q-959q-f8rh (MODERATE) —
mergeAttributes()turns an own__proto__key into inherited executable DOM attributes; affects>= 2.0.0-alpha.0, < 3.30.4. Studio callsmergeAttributeson attributes parsed from stored channel content (extensions/Image.js:42,extensions/Math.js:30,extensions/SmallTextExtension.js:29).
Both advisories list @tiptap/core as the only affected package, so the core-only bump is complete remediation.
Other changes in range: 3.30.0 adds a Decorations API and getPreviousBlockSibling($pos); 3.30.1 adds ProseMirror type guards; 3.30.2/3.30.3 fix editor.chain/editor.can on init and JSX-runtime sibling rendering. All additive — nothing Studio uses changes behaviour. The 3.30.0 ListKeymap Tab-sink change lives in @tiptap/extension-list-keymap, which stays at 3.29.0 and so does not land here.
suggestion — peer mismatch: tiptap pins peers exactly. @tiptap/extension-link@3.29.0 and @tiptap/vue-2@3.29.0 require '@tiptap/core': 3.29.0 (pnpm-lock.yaml:1712, :1788), and @tiptap/core@3.30.5 requires '@tiptap/pm': 3.30.5 (:1624) while the lockfile has only @tiptap/pm@3.29.0. Nothing breaks today (core is backward compatible within 3.x), but CI's silence is not evidence: install logs Lockfile is up to date, resolution step is skipped, and pnpm only reports peer issues during resolution. Merge for the fix, then follow with a bump of the whole @tiptap/* set to 3.30.5.
suggestion — .github/dependabot.yml: the existing tiptap group is why this arrived as a lone package — groups apply to version updates only unless a group sets applies-to: security-updates. Adding that entry would make future tiptap security bumps land as one coherent PR. Out of scope here.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
Bumps @tiptap/core from 3.29.0 to 3.30.5.
Release notes
Sourced from @tiptap/core's releases.
... (truncated)
Changelog
Sourced from @tiptap/core's changelog.
... (truncated)
Commits
b0c188bchore(release): release new stable release (#8261)d0d499bMerge commit from fork55f59e4chore(release): release new stable release (#8260)01d7af8Merge commit from fork98b469dchore: complete Vite+ migration (#8258)db790a7chore(release): release new stable release (#8216)f434577chore: migrate over to vite+ for tooling (#8151)965a880fix(core): preserve JSX child boundaries (#7491)cef2c9achore(release): release new stable release (#8190)214a140fixededitor.canandeditor.chainto not be accessible on editor … (#8210)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.